Technical Artifacts

Adapter Template

Interface/ Class	Purpose	Description
Service Contract [This layer has only the interface declaration.]	This layer has the interface class with method declarations. For example, AppFlowService (These methods are invoked by the controller to perform certain operations within the AppFlow tool.)	This interface class file is bundled within a JAR file and this dependency is added to the Gradle build file.
Service Implementation	This class (For example, AppFlowServiceImpl) contains the implementation for the methods declared within the interface. This implementation is tool-specific and should be implemented by the external development team.	To be implemented by the adapter development team.
Configuration Changes (Configurations, DB scripts)	These configurations are necessary to activate the new adapter within the Calibo Accelerate platform.	Early discussions should be held between the external development team and the core team. Based on these discussions, the core team will develop required configuration scripts with mandatory values and will execute them on the Calibo Accelerate platform to generate the required configurations.
Libraries	Spring boot and the required Lazsa-specific libraries will be supplied as dependencies in the template repository.	Supplied to the adapter development team as part of the template repository.

What's next? Adapter Integration with Lazsa